Node-RED block in Snap4City Microservice library node-red-contrib-snap4city-developer is "service-info-dev">
    <p>It allows to retrieve information about a service using its serviceUri.</p>

    <h3>Inputs</h3>
    A JSON with these parameters:

    <dl class="message-properties">
        <dt>serviceuri
            <span class="property-type">string</span>
        </dt>
        <dd> serviceUri (http://...) of the service</dd>
        <dt>fromtime
            <span class="property-type">string</span>
        </dt>
        <dd> fromtime, date/time from when retrieve realtime data. The string format can be: n-day, n-hour, n-minute or yyyy-mm-ddThh:mm:ss </dd>
        <dt>totime
            <span class="property-type">string</span>
        </dt>
        <dd> totime, date/time to when retrieve realtime data. The string format can be: yyyy-mm-ddThh:mm:ss </dd>
        <dt>valuename
        <span class="property-type">string</span>
            </dt>
        <dd> A service uri may have several values available. With valuename you can indicate which of the values you want to receive in response by filtering them out. </dd>
        <dt>lang
            <span class="property-type">string</span>
        </dt>
        <dd> ISO 2 chars language code (e.g. “it”, “en”, “fr”, “de”, “es”) to be used for returned descriptions if available in
            multiple languages. Currently for languages other than “it” and “en” it returns “en” descriptions. (if parameter
            is missing “en” is assumed)</dd>
    </dl>

    <h3>Outputs</h3>
    <dl class="message-properties">
        <dd> The It provides a GeoJSON description of the service with the main properties (name, address, city, type, etc.) and
            possibly some time varying properties for some kinds of services (traffic sensors, car park sensors, etc.)</dd>
    </dl>

    <h3>Details</h3>
    <p>The node can receive a JSON with the parameters described in the Inputs section and with them generate the output JSON.
        If the values are not present in the input JSON, these are read by those in the configuration. If they are not present
        in either part, an error is generated for the necessary parameters.</p>